…der` (hyperium#3006)

fix incomplete changes introduced from hyperium#2828

Previously, `to_bytes` would reserve extra space if after two chunks,
there was more remaining. It used to reserve however much space the peer
advertized.

This changes now only reserves up to ~16kb. This way, a slow message
with a big body doesn't reserve so much memory, until the data has
actually been received.

The existing warning to check for a length before calling the function
is still the best approach.

…yperium#3138)

Add `poison` method to `Connected`. This allows callers to mark a connection as poisoned which prevents the pool from reusing it on subsequent requests. `is_open` will consider poisoning prior to returning a connection to the pool.

)

Add `capture_connection` functionality. This allows callers to retrieve the `Connected` struct of the connection that was used internally by Hyper. This is in service of hyperium#2605.

Although this uses `http::Extensions` under the hood, the API exposed explicitly hides that detail.

This patch backports client/conn/http1 and http2 modules from 1.0 to
ease transition. It allows code still using 0.14.x to switch to the
per-version Connection types available in 1.0.

Closes hyperium#3053 

Co-authored-by: KOVACS Tamas <ktamas@fastmail.fm>

`client::conn::{SendRequest, Connection, Builder, handshake}` are deprecated as they are removed in 1.0.

This adds the `deprecated` feature to Cargo, and only when `hyper/deprecated` is enabled will these warnings be emitted.

Co-authored-by: KOVACS Tamas <ktamas@fastmail.fm>

…#3119)

…um#3102)

Closes hyperium#3079

…ion (hyperium#3201)

This allows users to set the configuration option from hyperium/h2#668.

…hyperium#2749)

…hyperium#3254)

Closes hyperium#3252

…ium#3256)

If a connection has any error besides reading, a streaming body
sometimes wouldn't be notified. This change makes it so that when a
connection task is closing because of any error, an existing body
channel is also notified.

Closes hyperium#3253

Allows adding headers with arbitrary casing
so that we can have headers that are all-caps,
all upper-case, or whatever else we want.

Co-authored-by: James Lucas <jaymell@users.noreply.github.com>

This allows case-sensitive headers to be added
by simply adding a HeaderCaseMap-typed extension
to the hyper Request object.

Co-authored-by: James Lucas <jaymell@users.noreply.github.com>